gn: Specifies to send the real APN name.
virtual: Specifies to send the virtual APN name if present, else to send the real APN name.
Default: gn
Important: This command is for a customer-specific implementation to support IP-CAN policy control via Gx interface in PDSN, wherein the PCRF informs the subscriber's subscription level (such as gold, silver, bronze) to PDSN/PCEF via Priority-Level AVP, then PDSN maps the subscriber's subscription level to inter-user-priority and transmits it to PCF via A11 session update message. For more information on the use of this command contact your Cisco account representative.This command configures the value of the Offline AVP sent to the PCRF based on the Charging Characteristics (CC) profile received from the SGSN.
cc_profile_number must be an integer from 0 through 15.
Specifies, for a range of CC profile numbers to map, the end number. That is, from cc_profile_number through cc_profile_number_range_end.
cc_profile_number_range_end must be an integer from 1 through 15.
Specifies to map the CC profile number(s) to the Offline AVP value sent to the PCRF.
|
•
|
0: Corresponds to the value DISABLE_OFFLINE (0).
|
|
•
|
1: Corresponds to the value ENABLE_OFFLINE (1).
|
Use this command to configure the CC Profile to Offline AVP value mapping. The Offline AVP’s value (DISABLE_OFFLINE (0), ENABLE_OFFLINE (1)) is derived based on the CC profile received from the SGSN as specified by this mapping.
When configuring this command, overlapping of CC profile numbers is not permitted. In the following example, after configuring the first command, which specifies to send the Offline AVP’s value as 1 (Offline enabled) for the CC profiles 1 through 15, the second command, which specifies to map CC profile 7, is not permitted:
The following command specifies to send Offline AVP value as 1 (Offline enabled) for the CC profile 1 (Hot Billing):
Important: This keyword is for use with a customer-specific implementation, and will be available only if a valid license is installed.
Important: This keyword is for use with a customer-specific implementation, and will be available only if a valid license is installed.dpca-custom6 ... dpca-custom20
Default: standard
The following command sets the standard dictionary for Diameter Policy Control functions in 3GPP network:
subscriber-limit subs_limit
Specifies the limit of subscribers to switch or reselect the PCRF for subscribers not more than subs_limit in time duration of duration second(s).
subs_limit must be an integer from 1 through 10000000.
time-interval duration
Specifies the time duration, in seconds, to reselect PCRF for subscribers not more than subs_limit in time duration of duration second(s).
duration must be an integer from 1 through 3600.
In case IMS authorization session have been opened on certain PCRF on the basis of the current selection table, and the current active table configuration is changed, the IMSA starts selection procedure for the PCRF. Existing sessions on current PCRF from earlier table is required to close and reopened on the selected PCRF from the new table. This reselection periodicity is controlled by this command and it indicates the number of subscriber sessions subs_limit to be reselected or moved in duration seconds.
For example, if this command is configured with 100 subscribers and 2 seconds, then the system reselects the PCRF for no more than 100 subscribers per 2 seconds.
The following command sets the system to reselect the new PCRF for no more than 1000 subscriber in 15 seconds:
diameter host-select row-precedence precedence_value table { { { 1 | 2 } host host_name [ realm realm_id ] [ secondary host host_name [ realm realm_id ] ] } | { prefix-table { 1 | 2 } msisdn-prefix-from msisdn_prefix_from msisdn-prefix-to msisdn_prefix_to host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] algorithm { active-standby | round-robin } ] } } [ -noconfirm ]
no diameter host-select row-precedence precedence_value table { { 1 | 2 } | prefix-table { 1 | 2 } }
diameter host-select row-precedence precedence_value table { 1 | 2 } host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] ]
row-precedence precedence_value: Specifies precedence of the row in the Diameter host table.
Important: In 8.1 and later releases, precedence_value must be an integer from 1 through 128. In 8.0 and previous releases, precedence_value must be an integer from 1 through 100.table { 1 | 2 }: Specifies the Diameter host table to add/append the primary and secondary Diameter host addresses.
host host_name: Specifies the primary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.
realm realm_id: Specifies the primary realm ID. realm_id must be an alphanumeric string of 1 through 127 characters in length.
secondary host sec_host_name [ realm sec_realm_id ]: Specifies the secondary host name and realm ID:
host sec_host_name: Specifies the secondary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.
realm sec_realm_id: Specifies the secondary realm ID. realm_name must be an alphanumeric string of 1 through 127 characters in length.
diameter host-select row-precedence precedence_value table prefix-table { 1 | 2 } msisdn-prefix-from msisdn_prefix_from msisdn-prefix-to msisdn_prefix_to host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] algorithm { active-standby | round-robin } ] [ -noconfirm ]
row-precedence precedence_value: Specifies precedence of the row in the table.
Important: In 8.1 and later releases, precedence_value must be an integer from 1 through 128. In 8.0 and previous releases, precedence_value must be an integer from 1 through 100.prefix-table { 1 | 2 }: Specifies the MSISDN prefix range table to add the primary and/or secondary Diameter host addresses.
msisdn-prefix-from msisdn_prefix_from: For a range of MSISDNs, specifies the starting MSISDN.
msisdn-prefix-to msisdn_prefix_to: For a range of MSISDNs, specifies the ending MSISDN.
Important: To enable the Gx interface to connect to a specific PCRF for a range of MSISDNs/subscribers configure msisdn_prefix_from and msisdn_prefix_to with the starting and ending MSISDNs respectively. The MSISDN ranges must not overlap between rows. To enable the Gx interface to connect to a specific PCRF for a specific MSISDN/subscriber, configure both msisdn_prefix_from and msisdn_prefix_to with the same MSISDN.host host_name: Specifies the primary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.
realm realm_id: Specifies the primary realm ID. realm_id must be an alphanumeric string of 1 through 127 characters in length.
secondary host sec_host_name [ realm sec_realm_id ]: Specifies the secondary host name and realm ID: host sec_host_name: Specifies the secondary host name. sec_host_name must be an alphanumeric string of 1 through 127 characters in length.
realm sec_realm_id: Specifies the secondary realm ID. sec_realm_id must be an alphanumeric string of 1 through 127 characters in length.
algorithm { active-standby | round-robin }: Specifies the algorithm for selection between primary and secondary servers in the MSISDN prefix range table.
Default: active-standby
active-standby: Specifies selection of servers in the Active-Standby fashion.
round-robin: Specifies selection of servers in the Round-Robin fashion.
Important: The Round Robin algorithm for PCRF selection is effective only over a large number of PCRF selections, and not at a granular level.The following command adds a row with precedence 12 in table 2 with primary host name as star_ims1 and secondary host name as star_ims2 to Diameter host table.
diameter host-select table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }
table { 1 | 2 }: Specifies the Diameter host table to obtain the primary and secondary host name for PCRF.
algorithm { ip-address-modulus [ prefer-ipv4 | prefer-ipv6 ] | msisdn-modulus | round-robin }: Specifies the algorithm to select row from the Diameter host table.
Default: round-robin
|
•
|
ip-address-modulus [ prefer-ipv4 | prefer-ipv6 ]: This algorithm divides the IP address, in binary, of the subscriber by the number of rows in the table, and the remainder is used as an index into the specified table to select the row.
|
|
•
|
msisdn-modulus: This algorithm divides the MSISDN value in binary without the leading “+” of the subscriber by the number of rows in the table, and the remainder is used as an index in the specific table to select the row.
|
|
•
|
round-robin: This algorithm rotates all rows in the active table for selection of the row in round-robin fashion. If no algorithm is specified this is the default behavior.
|
Important: The Round Robin algorithm is effective only over a large number of selections, and not at a granular level.The following command specifies table 1 with round-robin algorithm to select the rows with host name for E-PDF in Diameter host table.
diameter origin endpoint endpoint_name
endpoint endpoint_name
endpoint_name is the Diameter endpoint configured in Context Configuration Mode to bind with IMS authorization service, and must be an alpha/numeric string of 1 through 63 characters in length.
diameter request-timeout timeout
timeout must be an integer from 1 through 300.
Important: This command is applicable only to Diameter dictionaries that support standard based volume reporting over Gx feature.Release 12.0 onwards, if a 3GPP Rel. 7 based dictionary is already configured with diameter dictionary dpca-custom4 command, and then if the diameter update-dictionary-avps 3gpp-r9 command is applied, the Supported-Features AVP with feature bit 1 being set will be sent in the CCR-I to indicate that 3GPP Rel. 9 AVPs are also supported.
Both default and no command have the same behavior, as if the CLI command is not configured. Hence, in the output of show configuration verbose command, the default and no command is shown as no diameter update-dictionary-avps.
|
•
|
all: all triggers
|
|
•
|
pgw-trace-control: P-GW trace control change trigger
|
|
•
|
qos-change: QoS change trigger
|
|
•
|
rai-change: RAI change trigger
|
|
•
|
rat-change: RAT change trigger
|
|
•
|
sgsn-change: SGSN change trigger
|
|
•
|
ue-timezone-change: UE time zone change trigger
|
|
•
|
user-loc-change: User location change trigger
|
failure-handling { continue | retry-and-terminate | terminate | diameter-result-code { any-error | result_code } ccfh { continue | retry-and-terminate | terminate } [ cc-request-type { initial-request | terminate-request | update-request } ] }
no failure-handling diameter-result-code { any-error | integer result_code } [ cc-request-type { initial-request | terminate-request | update-request } ]
failure-handling cc-request-type { any-request | initial-request | terminate-request | update-request } { diameter-result-code { any-error | result_code [ to end_result_code ] } } { continue | retry-and-terminate | terminate }
no failure-handling cc-request-type { any-request | initial-request | terminate-request | update-request } [ diameter-result-code { any-error | result_code[ to end_result_code] } ]
any-error: Specifies failure handling behavior for those result-codes for which failure-handling behavior has not been specified.
result_code: Specifies a Diameter failure result code. result_code is the code returned for a failure handling action and must be an integer from 3000 through 4999.
to end_result_code: Use to specify a range of Diameter failure result codes. end_result_code must be an integer from 3000 through 4999, and must be greater than result_code.
|
•
|
continue: In the event of a failure the user session continues. DPCA/Diameter will make periodic request and/or connection retry attempts and/or will attempt to communicate with a secondary peer depending on the peer config and session-binding setting.
|
|
•
|
retry-and-terminate: In the event of a failure the user session continues for the duration of one retry attempt with the server. If this retry attempt also fails, the session is terminated.
|
|
•
|
terminate: In the event of a failure the user session is terminated.
|
|
•
|
continue: In the event of a failure the user session continues. DPCA/Diameter will make periodic request and/or connection retry attempts and/or will attempt to communicate with a secondary peer depending on the peer config and session-binding setting.
|
|
•
|
retry-and-terminate: In the event of a failure the user session continues for the duration of one retry attempt with the server. If this retry attempt also fails, the session is terminated.
|
|
•
|
terminate: In the event of a failure the user session is terminated.
|
|
•
|
any-request: Specifies the request type as any request for a new session.
|
|
•
|
initial-request: Specifies the request type as initial request for a new session.
|
|
•
|
terminate-request: Specifies the request type as terminate request for a session.
|
|
•
|
update-request: Specifies the request type as update request for an active session.
|
The following command sets the DPCA failure handling to retry-and-terminate and return a result code of 3456 for credit control request type initial-request:
Refer to the Cisco ASR 5000 Lawful Intercept Configuration Guide for a description of this command.
